Repository navigation
Conversation
|
We've flagged this as a potential contribution without a human behind it. We welcome the thoughtful use of AI tools when contributing, but ask all contributors to follow two core principles:
Please review these AI-assisted contribution guidelines and update this contribution if needed. We're closing this for now as the account looks automated. If we got that wrong, please just reopen the PR and we'll take another look. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1650 +/- ##
=======================================
Coverage ? 84.58%
=======================================
Files ? 183
Lines ? 11804
Branches ? 3381
=======================================
Hits ? 9985
Misses ? 1532
Partials ? 287 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Merging this PR will not alter performance1 warning
Comparing |
|
hey @danielroe , sorry for bothering again, but this PR was autoclosed |
🔗 Linked issue
📚 Description
nuxt buildcharged almost all the bundling tonitro: a one-file nuxt 5 app reportedclient 10ms · server 12ms · nitro 872ms. vite resolves every environment's config before bundling anything, andnitro:build:beforefires while nitro's config resolves, so we entered thenitrophase a few ms in.this adds a small vite plugin from
vite:extendand moves between phases on vite's ownbuildStartandcloseBundlehooks, soclient,serverandnitroeach get their own time. it also drops theexperimental.viteEnvironmentApicheck and its singleBundling appphase.